Read the contract once — know what's in scope forever
Paste contract or subcontract text; the extractor pulls every obligation statement ("shall / will / must / deliver / provide"). Classify each IN or OUT of scope with a note to the PM and customer. OUT / TBD items feed straight into the change-request process on the BidSummary. The slippage log below records every schedule slide with duration and reasoning.
Source: pasted contract / subK text (text-layer PDFs: copy & paste; scanned images need OCR — deployment stage). Classifications are the PM's call — the extractor finds candidates, it does not decide. Autosaved · a2e_scope_v1.
1 · Ingest a document
Name the document, paste its text, extract obligations.
OUT / TBD → change request: anything classified OUT of scope or TBD is your CR trigger. Take it to the BidSummary mod rollup with its delta financials — and if it moves dates, log the slide in the slippage log below with the reason.
2 · Classify scope
{{ scopeCounts }}
Click IN / OUT / TBD. The note goes to the PM and the customer record.
{{ s.text }}
{{ s.doc }}
3 · Schedule Slippage Log
Source: PM's schedule decisions. Every slide records the task, baseline vs. new date, computed slip duration, the reason, and the linked CR — this is the audit trail the customer sees.